Skip to main content
Waverley Borough Council

Brownfield land

There is a problem

  • 34 entries must have valid URIs

10a

SiteReference
10a
SiteNameAddress
Dunsfold Aerodrome, Stovolds Hill, Cranleigh
Deliverable
yes
HazardousSubstances
Hectares
214
MinNetDwellings
NetDwellingsRangeFrom
2600
NetDwellingsRangeTo
2600
OwnershipStatus
not-owned-by-a-public-authority
PermissionDate
2018-03-29
PermissionType
outline-planning-permission
PlanningHistory

PlanningHistory must be a real URL

PlanningHistory must be a real URL

http://planning360.waverley.gov.uk/planning/search-applications?civica.query.FullTextSearch=wa%2F2015%2F2395#VIEW?RefType=GFPlanning&KeyNo=279094&KeyText=Subject
PlanningStatus
permissioned
SiteplanURL
https://maps.waverley.gov.uk/map/Aurora.svc/run?script=%5CAurora%5CStatmap%20Aurora%20Brownfield%20Register.AuroraScript%24&nocache=9aa02e73-763a-978b-f18e-12c8a95acb41&resize=always
GeoX
POINT(-0.535632 51.116282)
GeoY
POINT(-0.535632 51.116282)
Notes
Site forms part of a larger promoted site which includes elements of greenfield, only the brownfield element has been included. This is a strategic site within the Waverley Local Plan Part 1 with an allocation of 2600 with planning permission granted for 1,800. Planning permission granted for new access road. Reserved matters application (access, appearance, landscaping, layout, scale) pursuant to outline permission for new roundabout within the site- pending decision
OrganisationLabel
OrganisationURI
LastUpdatedDate
2020-12-14
FirstAddedDate
2017-12-15
EndDate

How to fix this issue

Your dataset is missing the PlanningHistory column.

The Brownfield land guidance explains how to fix the issue:

PlanningHistory

Enter links to any web pages that give information on the site’s planning history (include the “http://” or “https://” prefix). Fields in this column can contain more than one link, as long as you separate multiple links with the pipe character (‘|’). You can leave this field blank.

How to improve Waverley Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL